Thien-Thi Nguyen <[EMAIL PROTECTED]> writes: > () Stefan Reichör <[EMAIL PROTECTED]> > () Thu, 03 Jul 2008 21:41:23 +0200 > > When I look at the log, I get the following: > > [log from branch "master"] > > So it seems that i can't find your changes... > > Sorry, i did not include clear instructions. Some background: > I left the branch "master" alone (it is a faithful clone of > git://git.hcoop.net/git/mwolson/emacs/dvc.git, w/o modification), > and made all my changes on branches whose names begin with "ttn-". > (Perhaps that's not recommended best-practice, i'm not sure. > mwolson: Any tips for the publishing-with-Git newbie?)
The master branch should have all of your changes -- it should not be a mirror of another repo. For major or invasive changes like whitespace, it is OK to make a branch that has these changes -- prefixing them with "ttn-" is also OK. Making a tag with a reference bzr revision seems like a good idea for these kinds of changes. For changes that are incremental, it might be good to run `C-x V l', and then hit `A' on each change to email it to the list. Configure xgit-mail-notification-destination to set which destination email address is used by default. As of the change I checked in a few minutes ago (which has also been checked in to my bzr repo), it will now be possible for Stefan to run `K T a' on the resulting commit message, which will apply it to his bzr repo and prepare a dvc-log-edit buffer for committing the change. The next step is to add authorship information as a local variable to the dvc-log-edit buffer, and teach the "commit" commands of various VCS's to use that information. -- | Michael Olson | FSF Associate Member #652 | | http://mwolson.org/ | Hobbies: Lisp, HCoop | | Projects: Emacs, Muse, ERC, EMMS, ErBot, DVC, Planner | `-------------------------------------------------------'
pgpbOu0pMwV26.pgp
Description: PGP signature
_______________________________________________ Dvc-dev mailing list [email protected] https://mail.gna.org/listinfo/dvc-dev
