summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@codesourcery.com>2015-01-22 16:12:59 +0100
committerThomas Schwinge <thomas@codesourcery.com>2015-01-22 16:12:59 +0100
commit8a8739902eddd5992b18ef39e03f9f55880c7d85 (patch)
treecbf6696961acb70e59e98b40660a8c6532eb9630
parent098dd44b0ac7202eca5285309322931fd101467a (diff)
source_repositories/glibc: Open Issue fixed.
... by removing stale refs/top-bases/youpi/* heads.
-rw-r--r--source_repositories/glibc.mdwn25
1 files changed, 2 insertions, 23 deletions
diff --git a/source_repositories/glibc.mdwn b/source_repositories/glibc.mdwn
index e31fac61..a1b60eab 100644
--- a/source_repositories/glibc.mdwn
+++ b/source_repositories/glibc.mdwn
@@ -1,5 +1,5 @@
-[[!meta copyright="Copyright © 2010, 2012, 2013, 2014 Free Software Foundation,
-Inc."]]
+[[!meta copyright="Copyright © 2010, 2012, 2013, 2014, 2015 Free Software
+Foundation, Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
@@ -115,24 +115,3 @@ Occasionally push new tags from the sourceware repository to the Savannah one:
$ git fetch sourceware
$ git tag | grep ^glibc- | sed 's%^%tag %' | xargs git push savannah
-
-
-# Open Issues
-
-## IRC, freenode, #hurd, 2013-12-13
-
- <braunr> is it ok to store several patches in one topgit branch ?
- <braunr> or is it really designed for one patch per branch ?
- <braunr> fatal: ambiguous argument 'origin/youpi/tls-threadvar': unknown
- revision or path not in the working tree.
- <braunr> tschwinge: ^
- <braunr> tschwinge: does that ring a bell ?
- <tschwinge> braunr: When/how did that happen?
- <tschwinge> Has the branch been removed from the origin remote?
- <tschwinge> Yes, has been deleted (on Savannah) on 2013-09-22.
- <tschwinge> Are you somehow referencing that branch?
- <braunr> tschwinge: tg remote --populate origin
- <tschwinge> braunr: Then I'd guess that Samuel has removed that branch but
- it is still referenced in some other branch's .topdeps file. I'll have a
- look (but don't hold your breath.)
- <braunr> tschwinge: sure