[libm4rie] 10/11: remove README.upstream, as it didn't correspond to the actual workflow

Cédric Boutillier boutil at moszumanska.debian.org
Mon Oct 20 11:57:56 UTC 2014


This is an automated email from the git hooks/post-receive script.

boutil pushed a commit to branch master
in repository libm4rie.

commit 8660b122110d58dc577ce6206e71aa0b33349872
Author: Cédric Boutillier <boutil at debian.org>
Date:   Sat Oct 18 21:52:17 2014 +0200

    remove README.upstream, as it didn't correspond to the actual workflow
---
 debian/README.upstream | 17 -----------------
 1 file changed, 17 deletions(-)

diff --git a/debian/README.upstream b/debian/README.upstream
deleted file mode 100644
index 3a86b63..0000000
--- a/debian/README.upstream
+++ /dev/null
@@ -1,17 +0,0 @@
-upstream uses mercurial at
-https://bitbucket.org/malb/m4rie
-
-i (felix) have pushed the repo created with
-git-hg clone https://bitbucket.org/malb/m4rie
-to alioth. i can now do
-git-hg fetch
-to get the upstream commits imported.
-
-unfortunately,
-git-hg clone https://bitbucket.org/malb/m4rie
-creates a git repo with commit ids different from the alioth repo.
-i have no clue how to reproduce a working instance, without messing with git-hg
-metadata.
-
-(it is still possible to rebase manually. however, this would render my git-hg
-repo useless, and enforce all future imports to be done manually)

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/debian-science/packages/libm4rie.git



More information about the debian-science-commits mailing list