Quoting Michael Olson <[EMAIL PROTECTED]>: > 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?
There's no fundamental difference, but you know this with the commiter ID, and using "bzr missing". You can also use the branch nick for that. It is recorded in each individual patch IIRC. > >> 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? for diff, it would be bzr diff -r ancestor:/the/branch/..last:1 ancestor:/the/branch means the common ancestor between your branch and /the/branch, and last:1 is the last revision in your branch. My internet connection and my bzr installs are half broken, I can't check with bundle right now. > >> 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! The choice here was not to /force/ people to give a name to the branch. The bzr team was particularly concerned about the first 5 to 10 minutes of use of the tool, and I believe they (as well as, at least Darcs and hg) managed to allow a user to actually do something with the tool within 10 minutes (while it takes more than that to understand the a/c--b--v namespace in Arch from my experience, especially for beginners who are not actually going to create several branches). But see below. > So what are branch nicknames supposed to be used for, then, if not > names of branches? OK, I missunderstood you. I thought you meant put your email address as the branch nick. OK, a hashtable "branch nick" -> "submission email" could be OK to me. That said, the branch will eventually contain the submission email, and there will also probably be a way to specify that address in ~/.bazaar/branches.conf, which allows wildcards on the branch location, so it will be possible to specify several submission adresses at the same time. This should be used when available. I'm not sure/I don't think it's worth having two ways to specify the submission address. In particular, I like the ability to change the tool depending on the use-case, and I'll probably be using DVC from time to time, and "bzr submit" from the command line from time to time. I expect to be able to configure both of them in the same configuration file. -- Matthieu ------------------------------------------------- envoyé via Webmail/IMAG ! _______________________________________________ Dvc-dev mailing list [email protected] https://mail.gna.org/listinfo/dvc-dev
