Re: openbsd version?

From: Daniel Barkalow <barkalow@iabervon.org>
Date: Oct 10, 2005, 21:31 UTC
Message-ID: <Pine.LNX.4.63.0510101703380.23242@iabervon.org>
In-Reply-To: <86y851aydl.fsf@blue.stonehenge.com>

On Mon, 10 Oct 2005, Randal L. Schwartz wrote:

Show 12 quoted lines

> >>>>> "Johannes" == Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> 
> >> <sarcasm>Undocumented secret switches.  Nice.</sarcasm>  No wonder
> >> I couldn't find it.
> 
> Johannes> <optimism>Maybe he who found the documentation lacking is going to fix 
> Johannes> it?</optimism>
> 
> I'd be happy to do that.  But as a tech writer, I know that it's
> insane to not work at least from an implementor's rough draft, to at
> least understand the intent of a mechanism, if not the precise design.
> There's no implementor's rough draft here, so I can't help.

The mailing list thread on the subject is at:

 http://www.gelato.unsw.edu.au/archives/git/0509/8902.html

(That's the middle of the thread, when the patch was actually written. There's discussion before and after if you need more info.)

You can actually get a pretty good explanation of features, once you know they exist at all, by looking for the discussion on the list. This tends to at least give you the person who did the patch explaining how to use it to the person who wanted the feature. And it'll also tell you who the implementor was, so you can bug the right person directly. :)

What does get written about a feature generall ends up in the commit message for the commit that adds it, so that's another good place to look. (In this case, it's missing a "not" and description of an option, so it's quite rough as a draft.)

In this case:

 "git branch -d <name>" deletes a branch with that name; but it checks 
that you're not on that branch, and it checks that that branch doesn't 
have any commits which aren't merged into the current branch.
 "git branch -D <name>" deletes a branch, and skips the second check.

	-Daniel
*This .sig left intentionally blank*