From: Holger Freyther <zecke@selfish.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: SCM scorecards
Date: Thu, 27 Mar 2008 17:50:49 +0100 [thread overview]
Message-ID: <200803271750.49583.zecke@selfish.org> (raw)
In-Reply-To: <fsggcu$5i8$1@ger.gmane.org>
On Thursday 27 March 2008 17:01:34 Koen Kooi wrote:
> Holger Freyther schreef:
> That's because you used the wrong branch include pattern when pushing,
> you did:
>
> ~ mtn push host org.foo.zecke1
>
> you want:
Why would I want to push my changes to the original branch? In this case I
don't want to because they contain untested changes.
This means I have to pull a 'virgin' org.openmoko.dev tree, pull my branches
from the other db and publish. Or kill the revisions in the org.openmoko.dev
branch I don't want to push.
>
> ~ mtn push host org.foo.{original,zecke1}
>
> the second will only transfer new revs, instead of marking all revs with
> the new branch cert and (re)transferring them.
Interesting. I thought the certs say which revision they are attached to, so I
would have to upload ~25.000 branch certs. The revisions should be unchanged
and only certs should be uploaded. I assume this is a bug and unnoticed due
the use of broadband. :)
thanks for the fish-slap, I was able to publish my two branches. So it is not
zero points on the scoreboard, but I hit one limitiation and one bug or just
two bugs. I will get my act together and report them.
z.
next prev parent reply other threads:[~2008-03-27 16:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 0:32 SCM scorecards Graeme Gregory
2008-03-27 0:50 ` Michael 'Mickey' Lauer
2008-03-27 1:01 ` Graeme Gregory
2008-03-27 2:11 ` Holger Freyther
2008-03-27 13:40 ` Mark Brown
2008-03-27 1:16 ` Rod Whitby
2008-03-27 2:26 ` Holger Freyther
2008-03-27 2:49 ` Holger Freyther
2008-03-27 16:01 ` Koen Kooi
2008-03-27 16:50 ` Holger Freyther [this message]
2008-03-27 16:15 ` Graeme Gregory
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=200803271750.49583.zecke@selfish.org \
--to=zecke@selfish.org \
--cc=openembedded-devel@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.