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] Further software updates after Coccinelle v1.0.5?
Date: Mon, 6 Jun 2016 22:26:04 +0200	[thread overview]
Message-ID: <12c45854-b1df-e9eb-98ed-8182585bae2f@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1606062203090.2060@localhost6.localdomain6>

>
>> * I would appreciate that corresponding changes will become viewable
>> also by the GitHub interface shortly.
> I have no idea what you are asking for.  The file changes.txt is availabl 
> in github all the time.

1. I have noticed that the last published commit seems to refer to a
merge (052860ee15849f96a856c253720261f350851771) from four days ago,
doesn't it?

2. A previous commit (from nine days ago) tried to express the message
"go back to version 1.0.4".

3. To which commit should the software release belong then after another
update for the involved version numbers?
   Was a Git tag introduced for the current revision identifier?

Regards,
Markus

  reply	other threads:[~2016-06-06 20:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-06  9:26 [Cocci] Coccinelle v1.0.5 Julia Lawall
2016-06-06 16:20 ` [Cocci] Further software updates after Coccinelle v1.0.5? SF Markus Elfring
2016-06-06 20:04   ` Julia Lawall
2016-06-06 20:26     ` SF Markus Elfring [this message]
2016-06-06 20:42       ` Julia Lawall
2016-06-06 20:50         ` SF Markus Elfring
2016-06-06 21:21           ` Julia Lawall
2016-06-06 21:32             ` SF Markus Elfring
2016-06-07 15:04             ` 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=12c45854-b1df-e9eb-98ed-8182585bae2f@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.