[EMAIL PROTECTED] wrote:
> Benjamin> Once you've pushed the branches, is there a way to remove them?
>
> Related question: is there a way to view the various branches in a non-local
> repository?
IIUC, conceptually, no. A branch is not *in* a repository; a branch *is*
a repository (*). So you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 30, 2008, at 3:35 AM, Martin v. Löwis wrote:
> Likewise, if you are accessing the repository over bzr+ssh, in
> general,
> you can just ssh to the machine, and do a regular ls. In the specific
>> Once you've pushed the branches, is there a way to remove them?
>
> Do you mean the local branches? If yes, then 'rm -rf mymergedbranch'
> does exactly what you want. :)
Notice that, unlike subversion, this will cause the entire branch
to go away, irrevocably (unless you had pushed it elsewhe
[EMAIL PROTECTED] wrote:
> Barry> All the gory details are documented here:
>
> Barry> http://www.python.org/dev/bazaar
>
> Thanks. I checked out, made a branch named test3, changed Makefile.pre.in
> to have a test3 target, checked it in, then tried to push it:
>
> % pwd
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 21, 2008, at 5:28 PM, Paul Moore wrote:
>
> One thing I really like the idea of with Mercurial for my situation
> (non-committer) is the mq extension, which lets me manage my changes
> as a "stack of patches" - so I'm completely working with pat
On Sat, Mar 22, 2008 at 8:28 AM, Paul Moore <[EMAIL PROTECTED]> wrote:
> Basically, can some Bazaar expert offer a suggestion as to how a
> non-developer with read-only access would best use the Bazaar
> repositories to maintain a number of patches to be posted to the
> tracker?
>
Here's what
On Fri, Mar 21, 2008 at 6:12 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
> On Fri, Mar 21, 2008 at 3:10 PM, Benjamin Peterson
> <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> >
> > On Fri, Mar 21, 2008 at 5:04 PM, Paul Moore <[EMAIL PROTECTED]> wrote:
> > >
> > > On 21/03/2008, Benjamin Peterson <[EMAIL
On Fri, Mar 21, 2008 at 3:10 PM, Benjamin Peterson
<[EMAIL PROTECTED]> wrote:
>
>
>
>
> On Fri, Mar 21, 2008 at 5:04 PM, Paul Moore <[EMAIL PROTECTED]> wrote:
> >
> > On 21/03/2008, Benjamin Peterson <[EMAIL PROTECTED]> wrote:
> > > I tend to make a repository and make a working copy for each patch
On Fri, Mar 21, 2008 at 5:04 PM, Paul Moore <[EMAIL PROTECTED]> wrote:
> On 21/03/2008, Benjamin Peterson <[EMAIL PROTECTED]> wrote:
> > I tend to make a repository and make a working copy for each patch in
> it.
> > The history is saved in the repository so it's efficient.
>
> OK, so just lots of
On 21/03/2008, Benjamin Peterson <[EMAIL PROTECTED]> wrote:
> I tend to make a repository and make a working copy for each patch in it.
> The history is saved in the repository so it's efficient.
OK, so just lots of copies, fair enough. Presumably just use bzr diff
to create patches? Much like Sub
On Fri, Mar 21, 2008 at 4:28 PM, Paul Moore <[EMAIL PROTECTED]> wrote:
> On 21/03/2008, Brett Cannon <[EMAIL PROTECTED]> wrote:
> > Just to head this off, this is not a specific vote of confidence for
> > Bazaar. The Bazaar developers were at PyCon and both Barry and Thomas
> > were willing to p
On 21/03/2008, Brett Cannon <[EMAIL PROTECTED]> wrote:
> Just to head this off, this is not a specific vote of confidence for
> Bazaar. The Bazaar developers were at PyCon and both Barry and Thomas
> were willing to put the time and effort to get the mirror up and going
> while the Bazaar team w
On Thu, Mar 20, 2008 at 2:49 PM, Christian Heimes <[EMAIL PROTECTED]> wrote:
> Barry Warsaw schrieb:
>
> > I'm happy to announce that we now have available for public
> > consumption, the Python source code for 2.5, 2.6 and 3.0 available
> > under the Bazaar distributed version control system.
>
13 matches
Mail list logo
