public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Brian Gladman <brg@gladman.plus.com>
To: Rhys Ulerich <rhys.ulerich@gmail.com>, gsl-discuss@sourceware.org
Subject: Re: Used git-bzr-ng to import bzr trunk into git master on Savannah
Date: Wed, 30 Oct 2013 22:16:00 -0000	[thread overview]
Message-ID: <5271852E.8040304@gladman.plus.com> (raw)
In-Reply-To: <CAKDqugSvZBRTuFgiGHLLwRe0Zr9mmO7dN-Yk5xPaNMYtSnaRmg@mail.gmail.com>

On 30/10/2013 21:56, Rhys Ulerich wrote:
> Just an update, bzr is turned off in the Savannah.
> 
>> I'd rather not use two separate VCSes if we can avoid it.  Maybe we
>> can have a develop-1 for 1.x, master for stable 1.x, and a develop-2
>> for 2.x.  That would let folk play with 2.x so that we can revisit
>> this decision in the context of tangible code changes.
> 
> Along those lines, up on Savannah git I've got three branches in place:
>   develop-1: Trunk for GSL 1.x releases
>   develop-2: Trunk for GSL 2.x releases
>   master:  Latest stable release, default branch on clone once
> 'oldmaster' is gone.
> 
> I'm thinking we treat develop-1 like we've been treating bzr and
> develop-2 is the wild west for 2.x development.  Bug fixes will need
> to go in both places.
> 
> Thoughts?

Great work Rhys, its great to be able to use GIT for GSL development - I
much appreciate your efforts on this.

The arrangement you suggest should work well.  I haven't tried a commit
yet but this has worked with other GIT repos so I would not expect to
have any problems with this.

   Brian

      reply	other threads:[~2013-10-30 22:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-28 22:03 Rhys Ulerich
2013-10-28 22:27 ` Patrick Alken
2013-10-29  2:33   ` Rhys Ulerich
2013-10-30 21:57     ` Rhys Ulerich
2013-10-30 22:16       ` Brian Gladman [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5271852E.8040304@gladman.plus.com \
    --to=brg@gladman.plus.com \
    --cc=gsl-discuss@sourceware.org \
    --cc=rhys.ulerich@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).