On Thu, Feb 24, 2011 at 4:46 AM, Guilherme Salgado wrote:
> On Wed, 2011-02-23 at 10:09 +0800, Jammy Zhou wrote:
> > Hi All,
> >
> > For some upstream projects, we don't use git-send-mail to send patch
> > for review. Take KDE/Kwin project for example, post-review and the
> > reviewboard[1] are us
On Wed, 2011-02-23 at 10:09 +0800, Jammy Zhou wrote:
> Hi All,
>
> For some upstream projects, we don't use git-send-mail to send patch
> for review. Take KDE/Kwin project for example, post-review and the
> reviewboard[1] are used for patch review. How shall we handle such
> kind of cases?
I supp
On Wed, 2011-02-23 at 11:19 +0800, Eric Miao wrote:
> Just a thought in the other way: will it be useful to to have some
> web crawler to collect those activities as long as we all use linaro
> email addresses? For mails like patch within, there should be some
> thing we can identify.
I don't thin
Just a thought in the other way: will it be useful to to have some
web crawler to collect those activities as long as we all use linaro
email addresses? For mails like patch within, there should be some
thing we can identify.
On Wed, Feb 23, 2011 at 10:09 AM, Jammy Zhou wrote:
> Hi All,
>
> For s
Hi All,
For some upstream projects, we don't use git-send-mail to send patch for
review. Take KDE/Kwin project for example, post-review and the
reviewboard[1] are used for patch review. How shall we handle such kind of
cases?
[1] https://git.reviewboard.kde.org/
Regards,
Jammy
On Wed, Feb 23, 2
On Tue, Feb 22, 2011, john stultz wrote:
> Add to the commit log:
> CC: Loïc Minier
> CC: patc...@linaro.org
> And git-send-email will add those entries to the outgoing mail.
Ah, so it's in the commit forever; I thought you were adding that at
send-email time; ok, thanks!
--
Loïc Minier
On Tue, 2011-02-22 at 22:18 +0100, Loïc Minier wrote:
> On Tue, Feb 22, 2011, john stultz wrote:
> > Yea. Since I still send out patches from both my employer and linaro
> > address, I can't utilize fixed git config values.
> >
> > I already put the effort in to make sure my linaro work has my
> >
On Tue, Feb 22, 2011, john stultz wrote:
> Yea. Since I still send out patches from both my employer and linaro
> address, I can't utilize fixed git config values.
>
> I already put the effort in to make sure my linaro work has my
> linaro.org address as the author on a patch by patch basis. And
>
On Tue, 2011-02-22 at 16:41 -0300, Christian Robottom Reis wrote:
> On Tue, Feb 22, 2011 at 06:58:28PM +, Dave Martin wrote:
> > OK, we have a tie ;) Who wins?
> >
> > On Tue, Feb 22, 2011 at 5:15 PM, Christian Robottom Reis
> > wrote:
> > > On Tue, Feb 22, 2011 at 05:02:41PM +, Dave Mar
On Tue, Feb 22, 2011 at 06:58:28PM +, Dave Martin wrote:
> OK, we have a tie ;) Who wins?
>
> On Tue, Feb 22, 2011 at 5:15 PM, Christian Robottom Reis
> wrote:
> > On Tue, Feb 22, 2011 at 05:02:41PM +, Dave Martin wrote:
> [...]
> > Use CC, not BCC.
> [...]
ME! :)
--
Christian Robottom
On 02/22/2011 10:59 AM, Guilherme Salgado wrote:
> I've been using the sendemail.cc config as well, but unfortunately it is
> not used by stgit. If you use stgit to send patches you'll have to
> copy /usr/share/stgit/templates/patchmail.tmpl to ~/.stgit and add a
> 'CC: patc...@linaro.org' line to
On Tue, 2011-02-22 at 15:59 -0300, Guilherme Salgado wrote:
> I've been using the sendemail.cc config as well, but unfortunately it is
> not used by stgit. If you use stgit to send patches you'll have to
> copy /usr/share/stgit/templates/patchmail.tmpl to ~/.stgit and add a
> 'CC: patc...@linaro.o
I've been using the sendemail.cc config as well, but unfortunately it is
not used by stgit. If you use stgit to send patches you'll have to
copy /usr/share/stgit/templates/patchmail.tmpl to ~/.stgit and add a
'CC: patc...@linaro.org' line to it.
I guess we should add these two tips to one of the
OK, we have a tie ;) Who wins?
On Tue, Feb 22, 2011 at 5:15 PM, Christian Robottom Reis
wrote:
> On Tue, Feb 22, 2011 at 05:02:41PM +, Dave Martin wrote:
[...]
> Use CC, not BCC.
[...]
On Tue, Feb 22, 2011 at 6:08 PM, Loïc Minier wrote:
> On Tue, Feb 22, 2011, Dave Martin wrote:
[...]
> T
On Tue, Feb 22, 2011, Dave Martin wrote:
> Do we need a policy on whether or not to use Bcc here?
>
> One argument for using Bcc is that it avoids replies from subscribers
> to the destination mailing lists from also being CC'd to
> patc...@linaro.org. Can your analysis cope with patc...@linaro.o
On Tue, Feb 22, 2011 at 5:15 PM, Christian Robottom Reis
wrote:
> On Tue, Feb 22, 2011 at 05:02:41PM +, Dave Martin wrote:
>> Do we need a policy on whether or not to use Bcc here?
>>
>> One argument for using Bcc is that it avoids replies from subscribers
>> to the destination mailing lists f
On Tue, Feb 22, 2011 at 05:02:41PM +, Dave Martin wrote:
> Do we need a policy on whether or not to use Bcc here?
>
> One argument for using Bcc is that it avoids replies from subscribers
> to the destination mailing lists from also being CC'd to
> patc...@linaro.org. Can your analysis cope w
On Tue, Feb 22, 2011 at 4:38 PM, Amit Kucheria wrote:
> Hi,
>
> We're required to cc patc...@linaro.org for all patches that we send
> upstream. bzr/launchpad users are already covered or will be shortly.
>
> For those using git-send-email to send patches (and you really should
> be), it might mak
18 matches
Mail list logo
