All of lore.kernel.org
 help / color / mirror / Atom feed
From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] The Coccinelle repository on GitHub
Date: Sun, 7 Feb 2016 09:43:58 +0100	[thread overview]
Message-ID: <56B703CE.9040704@users.sourceforge.net> (raw)
In-Reply-To: <20160206213356.GA15592@pl-59055.rocqadm.inria.fr>

> The two repositories are totally incompatible.

Thanks for another clarification around the handling of a previous partial
and 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)?
> 
> No chances at all. No merge possibility. The former repository needs to
> be deleted and the new one cloned.

Thanks also for this information.


> Not doing so would result in a big mess.

Now I find that there is a need to clarify further software transitions
and data migrations for pull requests, isn't it?
https://github.com/coccinelle/coccinelle/pulls?q=is%3Apr+is%3Aclosed

1. Would you like to look for possibilities to keep cross references
   consistent anyhow?

2. From which Git repositories are you going pull the next changes?

3. How should a potential confusion be avoided for developers
   who dared to try anything out already in their personal topic branches?
   https://github.com/coccinelle/coccinelle/network/members

Regards,
Markus

      reply	other threads:[~2016-02-07  8:43 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
2016-02-06 21:33   ` Sébastien Hinderer
2016-02-07  8:43     ` SF Markus Elfring [this message]

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=56B703CE.9040704@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.