On 7/16/11 10:38 AM, "Bertrand Bordage" <bordage.bertr...@gmail.com> wrote:
>> Would it be possible to make upload.py sent multiple commits? For >> casual contributors, a single commit is fine, but serious >> developers like Mike require the ability to upload multiple >> commits for a single issue. > > Yes, this will be possible. > Do you mean something like this ? > http://codereview.appspot.com/4754046/ > This is achieved with a simple "python upload.py HEAD~3" > There is 3 commits and the three patches follow each other in the patch set. > As you can see on some side-by-side diffs, there is still a lot of bugs to > squash. Why are we trying to eliminate git-cl? What is the problem it causes? If it's just that it's not maintained, why not just add it as part of our source tree, along with lily-git? I guess there isn't a GPL license statement with git-cl, so maybe that won't work. Chromium uses git-cl in the depot_tools: http://dev.chromium.org/developers/how-tos/depottools It's a bit of a heavy download compared with git-cl, but one can also get git-cl directly from chromium: http://src.chromium.org/svn/trunk/tools/depot_tools/README.git-cl http://src.chromium.org/svn/trunk/tools/depot_tools/git_cl.py Personally, I think git-cl makes things much easier, so I wouldn't be in favor of eliminating it. Thanks, Carl _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
