All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH] dim: Update docs for update-branches
Date: Mon, 12 Dec 2016 10:14:29 +0200	[thread overview]
Message-ID: <87bmwhva1m.fsf@intel.com> (raw)
In-Reply-To: <20161209215222.7tmw6ekjfjgqqfow@phenom.ffwll.local>

On Fri, 09 Dec 2016, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Thu, Dec 08, 2016 at 11:53:07PM +0200, Jani Nikula wrote:
>> On Thu, 08 Dec 2016, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
>> > It's been years since drm-intel had only one maintainer, and the
>> > primary use-case for dim ub was only to sync between machines. Update
>> > the docs to reflect this, to avoid misleading committers. Also update
>> > the maintainer-tools branch, which is something Paulo's script also
>> > does.
>> >
>> > Motivated because Paulo typed an actualize.sh script which does
>> > exactly what dim ub is meant to do.
>> >
>> > v2: Also update quickstart guide.
>> >
>> > v3: And spelling fixes.
>> >
>> > Acked-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
>> > Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
>> > ---
>> >  dim     |  3 +++
>> >  dim.rst | 11 ++++++-----
>> >  2 files changed, 9 insertions(+), 5 deletions(-)
>> >
>> > diff --git a/dim b/dim
>> > index e0551ace54e4..3e82de96b4ab 100755
>> > --- a/dim
>> > +++ b/dim
>> > @@ -1293,6 +1293,9 @@ function dim_update_branches
>> >  	dim_checkout drm-intel-next
>> >  	$DRY git reset --hard $DIM_DRM_INTEL_REMOTE/drm-intel-next
>> >  
>> > +	cd $DIM_PREFIX/maintainer-tools
>> > +	git pull --rebase
>> > +
>> 
>> Ooops?
>
> From the commit message: "Also update the maintainer-tools branch, which
> is something Paulo's script also does." This way dim update-branches
> updates everything, and I think that's good, I liked that idea from
> Paulo's script a lot.

Oh. Didn't expect that in a patch with "update docs" as the title.

I often run dim with the changes I'm developing, using branches other
than maintainer-tools, so I'm not entirely thrilled.

BR,
Jani.



> -Daniel
>
>> 
>> 
>> >  	update_rerere_cache
>> >  }
>> >  
>> > diff --git a/dim.rst b/dim.rst
>> > index 0c52ab43e400..b9cb41a2ba5b 100644
>> > --- a/dim.rst
>> > +++ b/dim.rst
>> > @@ -74,11 +74,8 @@ Setup git maintainer branches in the given prefix.
>> >  
>> >  update-branches
>> >  ---------------
>> > -Updates all maintainer branches. Only needs to be run to synchronize branches
>> > -between different machines (or maintainers fwiw). As long a given branch is
>> > -always maintained from the same machine, even if different branches are
>> > -maintained on different machines (by different maintainers), there's no need to
>> > -run this command.
>> > +Updates all maintainer branches. Useful to synchronize all branches when other
>> > +maintainers and committers pushed patches meanwhile.
>> >  
>> >  status
>> >  ------
>> > @@ -408,6 +405,10 @@ corresponding to this repository is defined by DIM_DRM_INTEL in your .dimrc.
>> >  You should also have directories called maintainer-tools, drm-tip (for
>> >  rebuilding the tree), and drm-intel-rerere for some dim-internal book-keeping.
>> >  
>> > +If someone else has pushed patches first resync using::
>> > +
>> > +   $ dim update-branches
>> > +
>> >  Applying patches to dinq is done in the main repository with::
>> >  
>> >      $ cat patch.mbox | dim apply-queued
>> 
>> -- 
>> Jani Nikula, Intel Open Source Technology Center

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-12-12  8:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08 17:49 [PATCH] dim: Update docs for update-branches Daniel Vetter
2016-12-08 21:53 ` Jani Nikula
2016-12-09 21:52   ` Daniel Vetter
2016-12-12  8:14     ` Jani Nikula [this message]
2016-12-12  9:20       ` Daniel Vetter
2016-12-12 10:43         ` Jani Nikula

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=87bmwhva1m.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.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 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.