* Managing linux-next tree for submitting patches @ 2012-11-21 5:36 Kumar amit mehta 2012-11-21 5:52 ` devendra.aaru 0 siblings, 1 reply; 8+ messages in thread From: Kumar amit mehta @ 2012-11-21 5:36 UTC (permalink / raw) To: kernelnewbies 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@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. -Amit ^ permalink raw reply [flat|nested] 8+ messages in thread
* Managing linux-next tree for submitting patches 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 0 siblings, 1 reply; 8+ messages in thread From: devendra.aaru @ 2012-11-21 5:52 UTC (permalink / raw) To: kernelnewbies 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. > -Amit > > _______________________________________________ > Kernelnewbies mailing list > Kernelnewbies at kernelnewbies.org > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies ^ permalink raw reply [flat|nested] 8+ messages in thread
* Managing linux-next tree for submitting patches 2012-11-21 5:52 ` devendra.aaru @ 2012-11-21 6:43 ` Kumar amit mehta 2012-11-21 6:51 ` devendra.aaru 0 siblings, 1 reply; 8+ messages in thread From: Kumar amit mehta @ 2012-11-21 6:43 UTC (permalink / raw) To: kernelnewbies 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 ^ permalink raw reply [flat|nested] 8+ messages in thread
* Managing linux-next tree for submitting patches 2012-11-21 6:43 ` Kumar amit mehta @ 2012-11-21 6:51 ` devendra.aaru 2012-11-21 7:01 ` Kumar amit mehta 0 siblings, 1 reply; 8+ messages in thread From: devendra.aaru @ 2012-11-21 6:51 UTC (permalink / raw) To: kernelnewbies On Wed, Nov 21, 2012 at 1:43 AM, Kumar amit mehta <gmate.amit@gmail.com> wrote: > 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 no i meant use the maintainer's git in that cases, not the next ^ permalink raw reply [flat|nested] 8+ messages in thread
* Managing linux-next tree for submitting patches 2012-11-21 6:51 ` devendra.aaru @ 2012-11-21 7:01 ` Kumar amit mehta 2012-11-21 7:47 ` devendra.aaru 0 siblings, 1 reply; 8+ messages in thread From: Kumar amit mehta @ 2012-11-21 7:01 UTC (permalink / raw) To: kernelnewbies On Wed, Nov 21, 2012 at 01:51:14AM -0500, devendra.aaru wrote: > On Wed, Nov 21, 2012 at 1:43 AM, Kumar amit mehta <gmate.amit@gmail.com> wrote: > > 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 > > no i meant use the maintainer's git in that cases, not the next So, my understanding is that To be more cautious, I should still be basing my work on linux-next tree and before sending the patch to the maintainer, I should do a dry run against the maintainer's tree. CMIIW. ^ permalink raw reply [flat|nested] 8+ messages in thread
* Managing linux-next tree for submitting patches 2012-11-21 7:01 ` Kumar amit mehta @ 2012-11-21 7:47 ` devendra.aaru 2012-11-21 8:36 ` Kumar amit mehta 0 siblings, 1 reply; 8+ messages in thread From: devendra.aaru @ 2012-11-21 7:47 UTC (permalink / raw) To: kernelnewbies On Wed, Nov 21, 2012 at 2:01 AM, Kumar amit mehta <gmate.amit@gmail.com> wrote: > On Wed, Nov 21, 2012 at 01:51:14AM -0500, devendra.aaru wrote: >> On Wed, Nov 21, 2012 at 1:43 AM, Kumar amit mehta <gmate.amit@gmail.com> wrote: >> > 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 >> >> no i meant use the maintainer's git in that cases, not the next > So, my understanding is that To be more cautious, I should still be basing my > work on linux-next tree and before sending the patch to the maintainer, I > should do a dry run against the maintainer's tree. CMIIW. that maintainer's tree is next tree so that next can pickup. once the next pics up your changes gets merged there in next. always its good to work against' maintainers trees, if its a fix then its better work on the maintainer's torvalds's tree otherwise the next tree in maintainer's repo ^ permalink raw reply [flat|nested] 8+ messages in thread
* Managing linux-next tree for submitting patches 2012-11-21 7:47 ` devendra.aaru @ 2012-11-21 8:36 ` Kumar amit mehta 2012-11-21 13:44 ` Greg Freemyer 0 siblings, 1 reply; 8+ messages in thread From: Kumar amit mehta @ 2012-11-21 8:36 UTC (permalink / raw) To: kernelnewbies On Wed, Nov 21, 2012 at 02:47:15AM -0500, devendra.aaru wrote: > that maintainer's tree is next tree so that next can pickup. once the > next pics up your changes gets merged there in next. > > always its good to work against' maintainers trees, if its a fix then > its better work on the maintainer's torvalds's tree otherwise the next > tree in maintainer's repo In past, I've been advised to base my work against linux-next tree. See the mail [1] from Greg K H. [1] http://www.spinics.net/lists/newbies/msg46076.html ^ permalink raw reply [flat|nested] 8+ messages in thread
* Managing linux-next tree for submitting patches 2012-11-21 8:36 ` Kumar amit mehta @ 2012-11-21 13:44 ` Greg Freemyer 0 siblings, 0 replies; 8+ messages in thread From: Greg Freemyer @ 2012-11-21 13:44 UTC (permalink / raw) To: kernelnewbies Kumar amit mehta <gmate.amit@gmail.com> wrote: >On Wed, Nov 21, 2012 at 02:47:15AM -0500, devendra.aaru wrote: >> that maintainer's tree is next tree so that next can pickup. once >the >> next pics up your changes gets merged there in next. >> >> always its good to work against' maintainers trees, if its a fix then >> its better work on the maintainer's torvalds's tree otherwise the >next >> tree in maintainer's repo >In past, I've been advised to base my work against linux-next tree. >See the mail [1] from Greg K H. > >[1] http://www.spinics.net/lists/newbies/msg46076.html > The linux kernel is too big with too many maintains for one simple rule to work. Linux-next is an aggregator for lots of maintainer trees. In many/most cases it is a good place to work. But some subsystems have their own trees where they test out patches for a while before sending the patches to linux-next. For those the maintainer may require the patches apply to their tree, not linux-next. Ext4 is an example of subsystem with 2 or 3 patch preparation trees. You have to know which tree to work against. No easy answer i know of. Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2012-11-21 13:44 UTC | newest] Thread overview: 8+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 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 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
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).