From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] The Coccinelle repository on GitHub
Date: Sat, 6 Feb 2016 16:12:39 +0100 [thread overview]
Message-ID: <56B60D67.3080802@users.sourceforge.net> (raw)
In-Reply-To: <20160205202627.GA9705@pl-59055.rocqadm.inria.fr>
> For those of you who were downloading Coccinelle from GitHub, we recommaend
> that you remove your current clone of the GitHub repository and do a fresh
>
> git clone https://github.com/coccinelle/coccinelle.git
Do try to indicate that the previous GitHub repository was not really compatible
with the repository for the complete software development history?
Are there any chances to achieve that a command like "git checkout master
&& git pull" will also work without merge conflicts (if the suggested fresh
software copy would be omitted)?
Regards,
Markus
next prev parent reply other threads:[~2016-02-06 15:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 20:26 [Cocci] The Coccinelle repository on GitHub Sébastien Hinderer
2016-02-05 21:11 ` SF Markus Elfring
2016-02-05 21:28 ` Sébastien Hinderer
2016-02-05 21:42 ` SF Markus Elfring
2016-02-05 22:07 ` Sébastien Hinderer
2016-02-06 8:21 ` SF Markus Elfring
2016-02-06 15:12 ` SF Markus Elfring [this message]
2016-02-06 21:33 ` Sébastien Hinderer
2016-02-07 8:43 ` SF Markus Elfring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56B60D67.3080802@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=cocci@systeme.lip6.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox