From: Thiago Jung Bauermann <thiago.bauermann@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Oguz Kayral <oguzkayral@gmail.com>, gdb ml <gdb@sourceware.org>
Subject: Re: GSoC Status Report #3
Date: Tue, 21 Jul 2009 18:15:00 -0000 [thread overview]
Message-ID: <200907211516.33161.thiago.bauermann@gmail.com> (raw)
In-Reply-To: <m38wiiezxs.fsf@fleche.redhat.com>
Em Terça-feira 21 Julho 2009 13:57:51 Tom Tromey escreveu:
> >>>>> "Thiago" == Thiago Jung Bauermann <thiago.bauermann@gmail.com>
> >>>>> writes:
>
> Thiago> Just to be clear: the GSoC work is NOT under the Archer
> Thiago> umbrella. So it doesn't have to follow the Archer rules. And I
> Thiago> strongly prefer that the branch name doesn't start with the
> Thiago> archer- prefix.
>
> That is fine by me. The only reason for the archer- prefix is to avoid
> clashes with any branch names from gdb; but probably any name including
> "oguz" is also unlikely to cause problems :-)
Awesome. What about "gsoc-oguz-python"? I know, creativity in coming up with
names is not one of my turn ons...
As for branch rules, since this will be Oguz' playground, I guess the only
rule is whatever makes him work productively, WDYT? :-)
Oguz, there are some git tips in
http://sourceware.org/gdb/wiki/ArcherBranchManagement which may help you
(e.g., merging from master, extracting a patch, etc.).
--
[]'s
Thiago Jung Bauermann
next prev parent reply other threads:[~2009-07-21 18:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <36a35d480907180812j398bb1ax8889ab1eefca9127@mail.gmail.com>
2009-07-21 2:04 ` Thiago Jung Bauermann
2009-07-21 17:04 ` Tom Tromey
2009-07-21 17:35 ` Thiago Jung Bauermann
2009-07-21 17:54 ` Oguz Kayral
2009-07-21 17:58 ` Oguz Kayral
2009-07-21 18:02 ` Tom Tromey
2009-07-21 18:15 ` Thiago Jung Bauermann [this message]
2009-07-21 18:20 ` Tom Tromey
2009-07-18 15:18 Oguz Kayral
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200907211516.33161.thiago.bauermann@gmail.com \
--to=thiago.bauermann@gmail.com \
--cc=gdb@sourceware.org \
--cc=oguzkayral@gmail.com \
--cc=tromey@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox