From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Christian Stimming <stimming@tuhh.de>,
"Shawn O. Pearce" <spearce@spearce.org>,
Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>,
Sam Ravnborg <sam@ravnborg.org>,
Xudong Guan <xudong.guan@gmail.com>,
Brett Schwarz <brett_schwarz@yahoo.com>
Cc: git@vger.kernel.org
Subject: git-gui i18n repo on repo.or.cz
Date: Sat, 21 Jul 2007 03:12:56 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0707210300490.14781@racer.site> (raw)
Hi people,
I proudly present...
http://repo.or.cz/w/git-gui/git-gui-i18n.git
It is meant to be rebased to git-gui's master pretty often. It has also a
mob branch where you can push your new changes into.
For those who do not know what a mob branch is: By using the URL
mob@repo.or.cz:/srv/git/git-gui/git-gui-i18n.git, without password,
_everybody_ can push into the branch named "mob" (but _only_ into that).
This facilitates participation without the need of a password, or commit
permissions, since it is mean to be pulled/cherry-picked by the repo
maintainer, who can decide what is good and what is bad. For the moment,
the maintainer is yours truly. If somebody volunteers, I am certainly not
sad.
I would like to ask people to not push with "+" into the mob branch, but
pull it instead, so that we do not lose any valuable data. It is probably
a good idea to send an email to the repo maintainer, too.
For the time being, I will rebase the master branch relatively often,
and try to stay on top of the mob branch.
At the moment, the repo contains three branches: master (which I would
like to be rebased onto git-gui's master quite frequently),
christian-orig, the patch series which Christian sent, and which branched
off git-gui's master roughly 8 days ago, and the mob branch.
Ciao,
Dscho
reply other threads:[~2007-07-21 2:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.64.0707210300490.14781@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=brett_schwarz@yahoo.com \
--cc=git@vger.kernel.org \
--cc=paolo.ciarrocchi@gmail.com \
--cc=sam@ravnborg.org \
--cc=spearce@spearce.org \
--cc=stimming@tuhh.de \
--cc=xudong.guan@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 NNTP newsgroup(s).