Matthieu Moy <[EMAIL PROTECTED]> writes: >> If you're doing commits, you've already got a private repository. >> My bzr-submit code (and related usage patterns) assume that you >> *don't* have a private repository: you basically just use >> upstream's version. > > Then, I have good news for you : > > You _do_ have a local repository ;-). > > $ bzr get --help > usage: bzr branch FROM_LOCATION [TO_LOCATION] > aliases: get, clone > [...]
How do I differentiate between patches that I have "recorded" locally, and those that have been incorporated in the repo that I'm tracking? >> If we want to address the case you bring up, we should tie it into >> dvc-changelog by adding a command that sends marked patches via email >> to a particular email address. > > That's an option. Another one is to send > > ancestor:/the/branch/to/which/you/sumit..last:1 > > which will send all the patches that the other guy doesn't have. How does this look when translated as actual bzr commands? >> Perhaps we could share some settings with these hypothetical >> routines, however, like mapping branch nickname to email address. > > branch nicknames are probably not meant for this. At least, that's not > how the bzr developers use it. That's one thing I don't like about bzr -- the lack of names for repositories. A URL/URI is not sufficient to compose a name! So what are branch nicknames supposed to be used for, then, if not names of branches? -- Michael Olson -- FSF Associate Member #652 -- http://www.mwolson.org/ Interests: Emacs Lisp, text markup, protocols -- Jabber: mwolson_at_hcoop.net /` |\ | | | IRC: mwolson on freenode.net: #hcoop, #muse, #PurdueLUG |_] | \| |_| Project involvement: Emacs, Muse, Planner, ERC, EMMS
pgp8D9ruPVDAW.pgp
Description: PGP signature
_______________________________________________ Dvc-dev mailing list [email protected] https://mail.gna.org/listinfo/dvc-dev
