From: gmate.amit@gmail.com (Kumar amit mehta)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Managing linux-next tree for submitting patches
Date: Wed, 21 Nov 2012 12:13:43 +0530 [thread overview]
Message-ID: <20121121064343.GC2743@gmail.com> (raw)
In-Reply-To: <CAHdPZaPT_dEpg-zDDusFYU6HFk7WJHf+bkWW=ztG90N=8fsYOA@mail.gmail.com>
On Wed, Nov 21, 2012 at 12:52:58AM -0500, devendra.aaru wrote:
> On Wed, Nov 21, 2012 at 12:36 AM, Kumar amit mehta <gmate.amit@gmail.com> wrote:
> > Hi,
> >
> > After some discussions that happened over kernel newbie mailing list in past,
> > I've managed to send some trivial patches to linux janitors and to relevant
> > maintainers. My patch base has been linux-next tree and I'm glad that some of
> > them got merged. Recently, for one of my patch, I got a reply from the
> > subsystem maintainer that my patch doesn't apply to his tree anymore and asked
> > me to do a refresh and try again. To make things clear, please find the steps
> > that I've followed to clone linux-next tree:
> > amit at ubuntu:~$ mkdir lkernel
> >
> > amit at ubuntu:~$ cd lkernel
> >
> > amit at ubuntu:~/lkernel$ git init
> > Initialized empty Git repository in /home/amit/lkernel/.git/
> >
> > amit at ubuntu:~/lkernel$ git remote add linux-next
> > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> >
> > amit at ubuntu:~/lkernel$ git fetch linux-next
> >
> > amit at ubuntu:~/lkernel$ git fetch --tags linux-next
> >
> > amit at ubuntu:~/lkernel$ git tag -l next-*
> > next-20120816
> > next-20120817
> > next-20120820
> > next-20120821
> > ............
> > ............
> > next-20121114
> > next-20121115 < -- --- (Most recent tag)
> >
> > amit at ubuntu:~/lkernel$ git checkout next-20121115 -b Nov-15
> >
> > amit at ubuntu:~/lkernel$ git branch
> > * Nov-15
> >
> > So *Nov-15* is my local branch and here I did some changes and did a commit
> > amit at ubuntu:~/lkernel$ git add <some file in staging directory>
> > amit at ubuntu:~/lkernel$ git commt -a
> >
> > amit at ubuntu:~/lkernel$ git status
> > # On branch Nov-15
> > nothing to commit (working directory clean)
> >
> > I forgot to send this patch for couple of days and maybe that was reason, my
> > patch couldn't apply(as mentioned by the subsystem maintainer). So still
> > being on my *Nov-15" branch, today(November 21, 2012), I invoked, following
> > commands to get the latest tags:
> >
> > amit at ubuntu:~/lkernel$ git branch
> > * Nov-15
> >
> > amit at ubuntu:~/lkernel$ git remote update
> > amit at ubuntu:~/lkernel$ git fetch linux-next
> > amit at ubuntu:~/lkernel$ git fetch --tags linux-next
> >
> > I was hoping to get new tags, but to my surprise there hasn't been any new
> > releases. This makes me think that something is wrong with my git setup.
> >
> > My git configuration:
> > amit at ubuntu:~/lkernel$ git config --list
> > user.name=<my name>
> > user.email=<my Email ID>
> > credential.helper=cache --timeout=3600
> > sendemail.smtpserver=<gmail smtp server>
> > sendemail.smtpserverport=<port>
> > sendemail.smtpencryption=<encryption>
> > sendemail.smtpuser=<my email ID>
> > color.ui=true
> > color.status=auto
> > color.branch=auto
> > push.default=matching
> > branch.autosetuprebase=always
> > core.repositoryformatversion=0
> > core.filemode=true
> > core.bare=false
> > core.logallrefupdates=true
> > remote.linux-next.url=git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> > remote.linux-next.fetch=+refs/heads/*:refs/remotes/linux-next/*
> > branch.master.remote=linux-next
> > branch.master.merge=refs/heads/master
> > branch.master.rebase=true
> >
> > Please confirm if everything is okay with my git setup and I need not worry if I
> > do not see any new tags for sometime.
> >
>
> the case is where in which the maintainer will have a new tree for the
> patches and next didnt' updated to the latest maintainer tree, and
> there is people who worked on the same thing and thats why it didn't
> applied.
Thank you for your reply.
So If I did a refresh (git remote update) and then again checked out the tree
with the latest tag(Note, that my previous branch was based off next-20121115
tag and even after 5 days I still see next-20121115 as the latest tag), I should
be fine ?
In case you've been monitoring linux-next tree, then can you please issue the
following command and post what you get.
$ git tag -l next-*|tail -n 1
next prev parent reply other threads:[~2012-11-21 6:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 5:36 Managing linux-next tree for submitting patches Kumar amit mehta
2012-11-21 5:52 ` devendra.aaru
2012-11-21 6:43 ` Kumar amit mehta [this message]
2012-11-21 6:51 ` devendra.aaru
2012-11-21 7:01 ` Kumar amit mehta
2012-11-21 7:47 ` devendra.aaru
2012-11-21 8:36 ` Kumar amit mehta
2012-11-21 13:44 ` Greg Freemyer
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=20121121064343.GC2743@gmail.com \
--to=gmate.amit@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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).