linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Dominic Sacré" <dominic.sacre@gmx.de>,
	"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
	linux-rt-users@vger.kernel.org, "Julia Cartwright" <julia@ni.com>
Subject: Re: Changing checksums of RT patches
Date: Sat, 11 Mar 2017 08:43:19 -0500	[thread overview]
Message-ID: <20170311084319.37f294b2@gandalf.local.home> (raw)
In-Reply-To: <alpine.DEB.2.20.1703111044300.4213@nanos>

On Sat, 11 Mar 2017 10:45:32 +0100 (CET)
Thomas Gleixner <tglx@linutronix.de> wrote:

> On Fri, 10 Mar 2017, Steven Rostedt wrote:
> > Just an FYI, especially if you are using my older scripts (I haven't
> > updated the ones I posted). I was asked when I do my upload of a new
> > version to copy to both the main and older directory. But my scripts
> > still moved the main to the older one when a new release went out. This
> > caused the checksums of the created .gz to change in the older
> > directory.
> > 
> > What I do now is to still upload to both main and older, but when I
> > have a new release, I simply delete the main one, as the older one
> > already exists.  
> 
> That double upload does not make sense. Upload it once to the older folder
> and make a link. kup supports that.
> 

OK, I'll have to update my scripts to do this.

Thanks,

-- Steve

      reply	other threads:[~2017-03-11 13:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-09  9:09 Changing checksums of RT patches Dominic Sacré
2017-02-10 18:54 ` Sebastian Andrzej Siewior
2017-02-13 22:56   ` Dominic Sacré
2017-02-13 23:15     ` Dominic Sacré
2017-02-14 14:18       ` Steven Rostedt
2017-02-14 18:42         ` Dominic Sacré
2017-02-14 18:57           ` Steven Rostedt
2017-02-15 13:38             ` Dominic Sacré
2017-02-15 13:52               ` Sebastian Andrzej Siewior
2017-02-15 14:50                 ` Dominic Sacré
2017-02-15 17:15                   ` Sebastian Andrzej Siewior
2017-02-28 18:03             ` Thomas Gleixner
2017-02-28 18:30               ` Steven Rostedt
2017-03-10 23:13               ` Dominic Sacré
2017-03-10 23:19                 ` Steven Rostedt
2017-03-11  2:27                   ` Julia Cartwright
2017-03-11  3:21                     ` Steven Rostedt
2017-03-11 11:14                     ` Dominic Sacré
2017-03-11 13:42                       ` Steven Rostedt
2017-03-11  9:45                   ` Thomas Gleixner
2017-03-11 13:43                     ` Steven Rostedt [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=20170311084319.37f294b2@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=bigeasy@linutronix.de \
    --cc=dominic.sacre@gmx.de \
    --cc=julia@ni.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).