Pranit Bauva <pranit.ba...@gmail.com> writes:
> Also, when such an idea for new feature comes up, it is better to
> implement it because let's say some developer is stuck in future and
> this new feature could help him but he doesn't have a clue that such a
> discussion happened some time ago. Thus saving him time and further
> effort.
>
> Anyways, How is the convention in git for these type of futuristic ideas?
Just keep it in mind without complicating the code, unless the idea
truly makes sense and has immediate use.
For example, I do not know how it would be useful to be able to
count up starting from 2 with an option --more that is COUNTUP, if
your --no-more would reset it to 0.
git cmd --more ;# sets more=2
git cmd --more --more ;# sets more=3
git cmd --no-more --more ;# sets more=1, not more=2
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
