From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Yann Dirson <ydirson@altern.org>
Cc: Josef Sipek <jsipek@fsl.cs.sunysb.edu>,
"Michael S. Tsirkin" <mst@dev.mellanox.co.il>,
Junio C Hamano <junkio@cox.net>,
Catalin Marinas <catalin.marinas@arm.com>,
git@vger.kernel.org, Josef 'Jeff' Sipek <jsipek@cs.sunysb.edu>
Subject: Re: using stgit/guilt for public branches
Date: Fri, 4 May 2007 01:10:33 +0200 [thread overview]
Message-ID: <200705040110.34697.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <20070503205836.GA19253@nan92-1-81-57-214-146.fbx.proxad.net>
torsdag 03 maj 2007 skrev Yann Dirson:
[...]
> As for publishing, I use the following config entries to publish my
> own stack of patches to stgit. You can see at
> http://repo.or.cz/w/stgit/ydirson.git that gitweb shows pretty clearly
> the structure of the stack (even though things could surely be made
> better).
>
> I use "git push -f" to publish - maybe the "+" refspec syntax would
> work with push, I'll try it next time :)
>
> [remote "orcz"]
> url = git+ssh://ydirson@repo.or.cz/srv/git/stgit/ydirson.git
> push = refs/heads/master:refs/heads/master
> push = refs/patches/master/*:refs/patches/master/*
Beautiful!!
I needed to change the update commit though for git to recognize the
refs/patches heads. Or is that only because I had initialized the repos
using v1.5.0 ?
-- robin
next prev parent reply other threads:[~2007-05-03 23:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 12:20 using stgit/guilt for public branches Michael S. Tsirkin
2007-04-25 19:18 ` Josef Sipek
2007-04-25 19:52 ` Michael S. Tsirkin
2007-04-25 20:40 ` Josef Sipek
2007-04-25 21:37 ` Robin Rosenberg
2007-05-03 20:58 ` Yann Dirson
2007-05-03 23:10 ` Robin Rosenberg [this message]
2007-05-03 23:31 ` Robin Rosenberg
2007-05-04 21:28 ` Yann Dirson
2007-05-04 5:20 ` Michael S. Tsirkin
2007-05-04 21:37 ` Yann Dirson
2007-05-04 23:12 ` Yann Dirson
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=200705040110.34697.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=catalin.marinas@arm.com \
--cc=git@vger.kernel.org \
--cc=jsipek@cs.sunysb.edu \
--cc=jsipek@fsl.cs.sunysb.edu \
--cc=junkio@cox.net \
--cc=mst@dev.mellanox.co.il \
--cc=ydirson@altern.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox