On Thu, Apr 3, 2008 at 12:22 AM, Alex Rousskov
[EMAIL PROTECTED] wrote:
On Thu, 2008-04-03 at 08:55 +1100, Robert Collins wrote:
On Wed, 2008-04-02 at 15:52 -0600, Alex Rousskov wrote:
On Thu, 2008-04-03 at 08:38 +1100, Robert Collins wrote:
On Wed, 2008-04-02 at 11:21 -0600, Alex
On Thu, 2008-04-03 at 12:57 +0200, Kinkie wrote:
IMO integration with other tools should use out-of-band information,
such as an extra mail header.
[MERGE] in the subject is good to interact with humans, but too flimsy
to be used with automated tools.
[MERGE] is used so humans can manually
On Tue, 2008-04-01 at 13:34 +1100, Robert Collins wrote:
On Tue, 2008-04-01 at 15:18 +1300, Amos Jeffries wrote:
I'm getting annoyed by bzr's method of handling bzr send emails.
As you may have noticed it adds the subject of the last commit to the
email. regardless of the message thats
On Wed, 2008-04-02 at 11:21 -0600, Alex Rousskov wrote:
I think an incomplete [MERGE] default subject would be much better
that the current behavior that will lead to _incorrect_ subjects.
In addition, a command line option to specify the subject should be
added.
Amos wasn't entirely
On Thu, 2008-04-03 at 08:38 +1100, Robert Collins wrote:
On Wed, 2008-04-02 at 11:21 -0600, Alex Rousskov wrote:
I think an incomplete [MERGE] default subject would be much better
that the current behavior that will lead to _incorrect_ subjects.
In addition, a command line option to
On Thu, 2008-04-03 at 08:55 +1100, Robert Collins wrote:
On Wed, 2008-04-02 at 15:52 -0600, Alex Rousskov wrote:
On Thu, 2008-04-03 at 08:38 +1100, Robert Collins wrote:
On Wed, 2008-04-02 at 11:21 -0600, Alex Rousskov wrote:
I think an incomplete [MERGE] default subject would be
On Wed, 2008-04-02 at 15:52 -0600, Alex Rousskov wrote:
On Thu, 2008-04-03 at 08:38 +1100, Robert Collins wrote:
On Wed, 2008-04-02 at 11:21 -0600, Alex Rousskov wrote:
I think an incomplete [MERGE] default subject would be much better
that the current behavior that will lead to
tor 2008-04-03 klockan 08:55 +1100 skrev Robert Collins:
You want just [MERGE] right ?
Yes, or at least make it skip changesets which is already on the target
branch (i.e. merged from the target) when selecting the subject to use..
Having it pick a subject based on what is a merge from the
On Tue, 2008-04-01 at 15:18 +1300, Amos Jeffries wrote:
I'm getting annoyed by bzr's method of handling bzr send emails.
As you may have noticed it adds the subject of the last commit to the
email. regardless of the message thats asked for manually during the send
process.
It would be good
On Tue, 2008-04-01 at 15:18 +1300, Amos Jeffries wrote:
I'm getting annoyed by bzr's method of handling bzr send emails.
As you may have noticed it adds the subject of the last commit to the
email. regardless of the message thats asked for manually during the
send
process.
It would be
On Tue, 2008-04-01 at 15:41 +1300, Amos Jeffries wrote:
No. I'm just using:
bzr send --mailto=squid-dev.squid-cache.org
and entering the message when it asks for one.
Is it popping up a gui client, or a text editor? Does it have a field
for setting a subject?
-Rob
--
GPG key
On Tue, 2008-04-01 at 15:41 +1300, Amos Jeffries wrote:
No. I'm just using:
bzr send --mailto=squid-dev.squid-cache.org
and entering the message when it asks for one.
Is it popping up a gui client, or a text editor? Does it have a field
for setting a subject?
Just a text editor (nano
12 matches
Mail list logo
