[1508] in BarnOwl Developers

home help back first fref pref prev next nref lref last post

Re: RFC: Cleaning up the Debian barnowl.git

daemon@ATHENA.MIT.EDU (Anders Kaseorg)
Thu Oct 29 18:17:23 2009

Resent-From: nelhage@mit.edu
Resent-To: barnowl-dev-mtg@charon.mit.edu
X-Original-To: nelhage@lunatique.mit.edu
Date: Sun, 14 Jun 2009 13:41:10 -0400 (EDT)
From: Anders Kaseorg <andersk@MIT.EDU>
To: Sam Hartman <hartmans@mit.edu>
cc: barnowl-dev@mit.edu
In-Reply-To: <tsl3aa33wjs.fsf@mit.edu>

On Sun, 14 Jun 2009, Sam Hartman wrote:
> (speaking with my Debian hat on, not my barnowl hat. I definitely agree=
=20
> that the barnowl master should only have one copy of commits.)
> [=E2=80=A6]
> In particular, is this just a size/cleanlyness issues, or are there=20
> other affects that are undesirable?

The biggest annoyance for me is that adding the debian remote to my=20
barnowl repository causes its gitk --all view to become twice as long. =20
It also causes a search for all commits that include some particular=20
message or touch some particular file (which I typically do in gitk or git=
=20
log --all) to return everything twice.  So I grafted most of the extra=20
stuff away locally, and figured it might be useful to turn that work into=
=20
something that would help everyone.

Admittedly, there isn=E2=80=99t a particular need for me to have the debian=
=20
remote.  We used to have a copy of the debian branch in the main=20
repository, but nelhage deleted it (perhaps for reasons similar to the=20
above?).

Anders

home help back first fref pref prev next nref lref last post