Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Kuten <ivan.kuten@promwad.com>
To: buildroot@busybox.net
Subject: [Buildroot] Ignored patches - WHY?
Date: Fri, 19 Oct 2007 01:44:39 +0300	[thread overview]
Message-ID: <4717E1D7.8080100@promwad.com> (raw)
In-Reply-To: <a63ecaf0710180612n7f2de529g361b037b40c34727@mail.gmail.com>

Sushi Sensei wrote:
> I have send some patches ( 0001534, 0001533, 0001532) this week with
> the Patch Tracking page, the week before I have send the same patches
> without notices of this inclusion or error, some patch was send 2 or 3
> week before and was ignored... There are some problem with this
> patches??

Sushi, regading this lockfile-progs patch:


Index: package/lockfile-progs/lockfile-progs.mk
===================================================================
--- package/lockfile-progs/lockfile-progs.mk	(revisi?n: 20228)
+++ package/lockfile-progs/lockfile-progs.mk	(copia de trabajo)
@@ -3,11 +3,12 @@
 # lockfile-progs
 #
 #############################################################
-LOCKFILE_PROGS_VERSION=0.1.10
+LOCKFILE_PROGS_VERSION=0.1.11
 LOCKFILE_PROGS_SOURCE:=lockfile-progs_$(LOCKFILE_PROGS_VERSION).tar.gz
 LOCKFILE_PROGS_SITE:=http://ftp.debian.org/debian/pool/main/l/lockfile-progs/
 LOCKFILE_PROGS_CAT:=$(ZCAT)
-LOCKFILE_PROGS_DIR:=$(BUILD_DIR)/lockfile-progs-$(LOCKFILE_PROGS_VERSION)
+#LOCKFILE_PROGS_DIR:=$(BUILD_DIR)/lockfile-progs-$(LOCKFILE_PROGS_VERSION)/sid
+LOCKFILE_PROGS_DIR:=$(BUILD_DIR)/sid
 LOCKFILE_PROGS_BINARY:=usr/bin/lockfile-create
....

What the meaning of
-LOCKFILE_PROGS_DIR:=$(BUILD_DIR)/lockfile-progs-$(LOCKFILE_PROGS_VERSION)
+LOCKFILE_PROGS_DIR:=$(BUILD_DIR)/sid

What does it mean "sid" ???

LOCKFILE_PROGS_DIR:=$(BUILD_DIR)/lockfile-progs-$(LOCKFILE_PROGS_VERSION)

this line is pretty good and I do not see a reason to change it. Do you?

Best regards,
Ivan
--------------------------------
Embedded Linux engineer,
Promwad Company: http://www.promwad.com/
Homepage : http://www.ivankuten.com/
--------------------------------

  parent reply	other threads:[~2007-10-18 22:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-18 13:12 [Buildroot] Ignored patches - WHY? Sushi Sensei
2007-10-18 13:25 ` Ulf Samuelsson
2007-10-18 15:25 ` Kuten Ivan
2007-10-18 13:31   ` Ulf Samuelsson
2007-10-18 13:47     ` Sushi Sensei
2007-10-18 18:04       ` Erik Andersen
2007-10-18 19:12         ` Ivan Kuten
2007-10-18 18:12           ` Sushi Sensei
2007-10-18 22:21 ` Ivan Kuten
     [not found]   ` <4717DAC8.5050209@gmail.com>
2007-10-18 23:36     ` Ivan Kuten
2007-10-18 23:47       ` Ulf Samuelsson
2007-10-18 22:44 ` Ivan Kuten [this message]
2007-10-18 23:02   ` Ivan Kuten
2007-10-18 22:10     ` Rex Luscus

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=4717E1D7.8080100@promwad.com \
    --to=ivan.kuten@promwad.com \
    --cc=buildroot@busybox.net \
    /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