Re: Question about .git/objects/info/alternates

From: Chris Packham <judge.packham@gmail.com>
Date: Mar 24, 2010, 20:37 UTC
Message-ID: <a038bef51003241337p61705a35kd5ab6943bb27de36@mail.gmail.com>
In-Reply-To: <780e0a6b1003241316i4bbd4489w63ba0308706e4d20@mail.gmail.com>

On Wed, Mar 24, 2010 at 1:16 PM, Stephen Boyd <bebarino@gmail.com> wrote:

Show 19 quoted lines

> On Wed, Mar 24, 2010 at 11:53 AM, Chris Packham <judge.packham@gmail.com> wrote:
>>
>> +USAGE='[-r|--recursive] [-a|--add <dir>] [-f|--force -d|--delete <dir>]'
> [...]
>> +case $oper in
>> +    add) add_alternate ;;
>> +    del) del_alternate ;;
>> +    *)   show_alternates ;;
>> +esac
>
> From a very high-level this should probably be more like git remote
> and git notes. 'add' and 'delete' would be subcommands instead of
> options. Plus you might have an explicit subcommand for show (or
> list?). Something like
>
> git alternates [show]  [-r|--recursive]
> git alternates add <dir>
> git alternates delete  [-f|--force] <dir>
>

I like that suggestion. I'd have to figure out the option parsing but should be doable. This is of course assuming it remains its own command set and isn't rolled into something else.