You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by Garret Pick <pickgr@pv.com> on Thu Feb 26 11:05:35 PST 2009
Source: JIRA REPO-9
From
http://groups.google.com/group/repo-discuss/browse_thread/thread/20a4f3fb82f49cf
7
An error I saw from repo prune. Note that the second time I ran it, it seemed
to work fine.
$ repo prune
Pending Branches
project bionic/
Traceback (most recent call last):
File "/home/pickgr/master/.repo/repo/main.py", line 202, in <module>
_Main(sys.argv[1:])
File "/home/pickgr/master/.repo/repo/main.py", line 186, in _Main
repo._Run(argv)
File "/home/pickgr/master/.repo/repo/main.py", line 96, in _Run
cmd.Execute(copts, cargs)
File "/home/pickgr/.repo/repo/subcmds/prune.py", line 52, in Execute
File "/home/pickgr/master/.repo/repo/project.py", line 126, in
commits
'--')
File "/home/pickgr/master/.repo/repo/project.py", line 1174, in
rev_list
p.stderr))
error.GitError: platform/bionic rev-list ('--abbrev=8', '--abbrev-
commit', '--pr
$
$
$ repo prune
$ git status
# Not currently on any branch.
nothing to commit (working directory clean)
$
Original issue reported on code.google.com by code-rev...@gtempaccount.com on 24 Sep 2009 at 9:09
The text was updated successfully, but these errors were encountered:
Comment by Shawn Pearce <sop@google.com> on Mon Mar 02 12:20:53 PST 2009
This is caused by a change to git branch -d's output.
Prior to Git version v1.6.1-rc3~5 the output of bit branch matched:
Deleted branch (.*)\.
where the subgroup grabbed the branch name. In v1.6.1-rc3~5 (aka
a126ed0a01e265d7f3b2972a34e85636e12e6d34) Brandon Casey changed the output to
include the SHA-1 of the branch name, now matching the pattern:
Deleted branch (.*) \([0-9a-f]*\)\.
That's what I get for making repo script against porcelain and not plumbing.
Original comment by code-rev...@gtempaccount.com on 24 Sep 2009 at 9:10
Original issue reported on code.google.com by
code-rev...@gtempaccount.com
on 24 Sep 2009 at 9:09The text was updated successfully, but these errors were encountered: