"submit" command naming - just "bundle" preferred?

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Aaron Bentley wrote:
> Adeodato Simó wrote:
> 
>> First, I must say I'd find desirable to have the command capable of be
>> invoking the user's editor to write the body, and have bzr send the
>> message. I won't argue whether this should be the default mode or not,
>> just stating that it'd be nice to have.
> 
> But does the world really need another mail client?  Especially when
> mutt behaves like that already?
> 

mutt does, but Mail.app, Thunderbird, Outlook, Evolution.... there are lots of
mail programs out there that people prefer to mutt. (I don't know whether pine
does/doesn't, but it seems like it could). And consider using 'gmail' :)

I could see it being configurable via ~/.bazaar/bazaar.conf. So that *if* you
have a mail program which we know how to spawn and set a To: and attachment,
and whatever else we need, then we do so. Otherwise we spawn $EDITOR, and send
ourselves using smtplib. Heck, this is already mostly done by bzr-email using
'post_commit_mailer=' (mail/smtplib).


>> Now, for spawning the user's prefered MUA to send the message, I propose
>> to use xdg-email program [1] from the FreeDesktop.org project.
> 
> It doesn't seem to be installed on my Etch.  Is it very popular?

It sounds like it would be useful if it was available.

> 
>>> 2. how do we configure the target address?
>> I guess the answer is "in branch.conf".
> 
> That's not really what I was asking.  Given that we'll use our normal
> configuration mechanism, what values will we use?  How's the policy
> supposed to work?

Sure, this is something that:
http://bazaar-vcs.org/SubmitByMail

was meant to address.

I think what we discussed (all the way back in Montreal), was that we would
have 2 values. One for the email address that *I* will send to when using this
branch, and one that other people who branch from me should use. Though it
would probably be sufficient in a first pass to have a single value that just
propagated by 'bzr branch'. Since people will be branching from the 'official
mainline' most of the time, and thus sending to the 'official mailing list'.
Rather than having the public location be the place you use to send to the pqm.

> 
> Will the mail attachments have sensible names?  Can I configure Bazaar
> to stick them in a particular directory instead of a temp one?

I would think we should create temporary ones, send them, and then delete them
once they are sent. So it seems to make more sense to always put them in temp.

We could certainly come up with a way to name them (branch-nick + revno +
$RANDOM + .patch).


I know I always use ~/dev/bzr/patches/$BRANCH_NICK.patch, and I have an alias
to create them for me.
alias BCB='bzr bundle $HOME/dev/bzr/bzr.dev > $HOME/dev/bzr/patches/`basename
$(pwd)`.patch'


But mostly that is just to work around the fact that we don't have a clean 'bzr
submit' command that lets me easily write comments about it before sending it
to the mailing list.

> 
>> Pardon my ignorance then, but
>> how is this useful if that file is not copied when branching?
> 
> It doesn't have to be copied to have sensible values.  If you want to
> clone a branch, cp -a will do that for you.  'branch' is for intelligent
> branching.
> 
> One option is to copy the target values.  But the target might be
> different for the mainline and branches derived from it.  It would be
> nice if branching from bzr.dev produced a branch with a different target
> from bzr.dev's own target, for example.

True, though bzr.dev doesn't actually need a target. It never pushes anywhere.
Everyone else pushes (through the PQM) to it.

> 
>>> Given a send command that actually sends mail, this is pretty good.  -o
>>> will be rarely used, for sure.
>> I'm curious, what's the use case for send -o, instead of using bundle -o?
> 
> This in the context of considering 'send' a total replacement for 'bundle'.
> 
> Aaron

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGn7u+JdeBCYSNAAMRAg4bAKDLYoF+i4PVoN0MAtQ/tyN8Z7YleACfcnpM
CyCkZo2/8xwmWztbV8kJZJs=
=rsQp
-----END PGP SIGNATURE-----