On 24 January 2011 16:25, Micah Gersten <[email protected]> wrote: > On 01/24/2011 10:16 AM, Barry Warsaw wrote: >> On Jan 24, 2011, at 10:09 AM, Micah Gersten wrote: >> >>> I actually wanted to add more features to debcommit like passing an >>> author name. It might be easier to try to standardize on debcommit so >>> that it's portable across multiple VCSs. Making bzr commit call >>> --fixes also sounds good for those that strictly use bzr. >> >> One of the reasons why I want to improve and recommend 'bzr commit' is that >> when using UDD, bzr is your front-end for most of the work. It seems jarring >> to have to remember to switch to debcommit for a step. Perhaps OTOH, >> debcommit should be recommended everywhere, but then, that seems jarring to >> someone used to using bzr. (We already recommended dch but that doesn't seem >> as bad because it doesn't really mirror a standard bzr command.) >> >> -Barry > > Right, but debcommit is the same as with any other VCS. You run VCS > foo, dch, and debcommit. <-- I wonder if debcommit is actually used > like this, I know that's what it's intended for, but it would be > interesting to know if it's actually used like that, especially with git. >
I have used before: debcheckout, dch, debcommit. I do this for Debian packages. For ubuntu packages I tend to use: bzr branch lp:ubuntu/* dch `bzr commit' `bzr push' I would like to have `bzr debcommit' - commit on steroids =) > Micah > > -- > ubuntu-distributed-devel mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel > -- ubuntu-distributed-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
