Git development
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@ucw.cz>
To: git@vger.kernel.org
Subject: [ANNOUNCE] git-pb git tree
Date: Wed, 11 May 2005 05:16:13 +0200	[thread overview]
Message-ID: <20050511031613.GO26384@pasky.ji.cz> (raw)

  Hello,

  I've published the git-pb git tree. This is a purely "core GIT" tree,
with no traces of Cogito itself inside, and intended to be safe-to-pull
for Linus. It will hopefully be soon fully synchronized by the GIT part
of the Cogito tree (it already has all the important bits), and will
stay so - any GIT stuff will go to the Cogito tree through the git-pb
tree.

  I plan to integrate the well-looking core git patches flying through
the mailing list to the git-pb tree, as well as various own stuff
(related or not related to what Cogito needs for operating well).  I
will be pulling from Linus on regular basis, and from git-jc too if I
feel comfortable with what's inside.

  I'm also thinking about git-pbc for the possibly controversial stuff
(taking care of hidden files, perhaps librarifications).


  You get it as a Git tree at

	rsync://rsync.kernel.org/pub/scm/cogito/git-pb.git
	http://www.kernel.org/pub/scm/cogito/git-pb.git


  On related note, I've set up a Git->CIA gateway. CIA is a commit
aggregator, tracking large number of open source projects. Cogito's and
git-pb's corner is at http://cia.navi.cx/stats/project/Cogito, the
commits are also broadcasted to the #git OPN channel (which is the point
of the whole thing, after all ;-).


  Have fun,

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor

             reply	other threads:[~2005-05-11  3:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-11  3:16 Petr Baudis [this message]
2005-05-11  4:11 ` [ANNOUNCE] git-pb git tree Junio C Hamano

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=20050511031613.GO26384@pasky.ji.cz \
    --to=pasky@ucw.cz \
    --cc=git@vger.kernel.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