On Mon, 18 Aug 2008 20:58:37 -0700
"Patrick McCarty" <[EMAIL PROTECTED]> wrote:
> On Mon, Aug 18, 2008 at 6:37 PM, Han-Wen Nienhuys <[EMAIL PROTECTED]>
> wrote:
> > If we start adding a lot of (occasional) contributors, I propose we
> > use the git.or.cz fork mechanism. People can then publish th
On 8/18/08 2:01 PM, "John Mandereau" <[EMAIL PROTECTED]> wrote:
>> I think it would also be easier to have a separate branch for the docs
>> because it would facilitate debugging -- there are lots more docs commits
>> than code commits, so it's hard (for me at least) to do a good job of
>> bise
Patrick McCarty wrote Tuesday, August 19, 2008 4:58 AM
On Mon, Aug 18, 2008 at 6:37 PM, Han-Wen Nienhuys <[EMAIL PROTECTED]>
wrote:
If we start adding a lot of (occasional) contributors, I propose we
use the git.or.cz fork mechanism. People can then publish their
changes, and it's easy for t
On Mon, Aug 18, 2008 at 6:37 PM, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
> If we start adding a lot of (occasional) contributors, I propose we
> use the git.or.cz fork mechanism. People can then publish their
> changes, and it's easy for the maintainers to pull/cherry-pick thoses.
I believe G
If we start adding a lot of (occasional) contributors, I propose we
use the git.or.cz fork mechanism. People can then publish their
changes, and it's easy for the maintainers to pull/cherry-pick thoses.
On Mon, Aug 18, 2008 at 5:01 PM, John Mandereau
<[EMAIL PROTECTED]> wrote:
> 2008/8/18 Carl D.
2008/8/18 Carl D. Sorensen <[EMAIL PROTECTED]>:
> Some time in the past, there was a request for a separate git
> repository/branch[1] for documentation, with the idea that more people could
> be approved for push access on the docs repository/branch than would be
> approved for push access on the
You can limit yourself to those by doing
git log -- lily/ scm/
I think bisect supports that too.
On Mon, Aug 18, 2008 at 11:49 AM, Carl D. Sorensen <[EMAIL PROTECTED]> wrote:
> Some time in the past, there was a request for a separate git
> repository/branch[1] for documentation, with the idea
Some time in the past, there was a request for a separate git
repository/branch[1] for documentation, with the idea that more people could
be approved for push access on the docs repository/branch than would be
approved for push access on the code.
I think it would also be easier to have a separat
