public inbox for
 help / color / mirror / Atom feed
From: Mark Wielaard <>
To: Pekka Enberg <>
Cc: Andrew Haley <>, Matthias Klose <>,, GCC Java <>,
	Dr Andrew John Hughes <>
Subject: Re: [cp-patches] tagging classpath for GCC import
Date: Mon, 03 Dec 2012 12:31:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, 2012-12-03 at 12:43 +0200, Pekka Enberg wrote:
> On Mon, Dec 3, 2012 at 12:04 PM, Mark Wielaard <> wrote:
> > There is the classpath git tree at
> >
> > which does have all that. But it only has the CVS part of the history.
> > The trick now is to figure out how to merge that git tree with the
> > official GNU Classpath git tree on savannah. Sadly my git foo isn't
> > strong enough to figure that out :{
> > So any hints or tips from some more experienced git users appreciated.
> The mirror git tree is where we branched off our current development
> tree. You should be able to just push the tags to the tree on
> Savannah. Andi?

aha, they are indeed mostly the same, though there is one commit that
doesn't match (the top one in the mirror, is also present on savannah
but under another commit id) which makes things slightly confusing. So
in principle git push --tags should do it, but how about the branches?



  reply	other threads:[~2012-12-03 12:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
     [not found] ` <>
2012-12-03  1:15   ` Matthias Klose
2012-12-03  7:15     ` Matthias Klose
2012-12-03  9:05     ` Mark Wielaard
2012-12-03  9:29       ` [cp-patches] " Andrew Haley
2012-12-03 10:04         ` Mark Wielaard
2012-12-03 10:44           ` Pekka Enberg
2012-12-03 12:31             ` Mark Wielaard [this message]
2012-12-03 15:00     ` Andrew Hughes

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:

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

  git send-email \ \ \ \ \ \ \ \ \

* 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).