git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Stimming <stimming@tuhh.de>
To: Paul Mackerras <paulus@samba.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] gitk: Update German translation
Date: Sat, 3 May 2008 10:03:09 +0200	[thread overview]
Message-ID: <200805031003.09458.stimming@tuhh.de> (raw)
In-Reply-To: <18460.6645.918108.615194@cargo.ozlabs.ibm.com>

Am Samstag, 3. Mai 2008 09:53 schrieb Paul Mackerras:
> Christian Stimming writes:
> > > Well, the commits aren't in date order, strictly speaking, and the
> > > last commit isn't necessarily the oldest (though the first commit will
> > > in fact be the newest).  How about:
> > >
> > > <Home>	Move to head of list
> > > <End>	Move to tail of list
> > >
> > > Would that be any clearer?
> >
> > I think "head of list" and "tail of list" are more the terms about the
> > implementation detail and not so much an explanation that is easily
> > understood for the user. I think some combination using the word "top"
> > should rather be used to make it really clear we're talking about the
> > upper end of the window.
>
> The list isn't just a detail, it's what the user sees in the top pane:
> the commits, listed in some order.
>
> How about "top of list" and "bottom of list"?  Or "start of list" and
> "end of list"?

I think "top of list" and "bottom of list" would work quite well.

Regards,

Christian

  reply	other threads:[~2008-05-03  9:21 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-01 19:42 [PATCH] gitk: Update German translation Christian Stimming
2008-05-01 21:10 ` Stephan Beyer
2008-05-02 19:23   ` Christian Stimming
2008-05-03  1:24     ` Stephan Beyer
2008-05-07 20:56       ` Christian Stimming
2008-05-15 16:20         ` Stephan Beyer
2008-05-24 20:48           ` Christian Stimming
2008-05-25 21:57             ` Stephan Beyer
2008-05-02 19:36   ` [PATCH] gitk: German translation again updated Christian Stimming
2008-05-02 11:49 ` [PATCH] gitk: Update German translation Paul Mackerras
2008-05-02 18:33   ` Christian Stimming
2008-05-03  7:53     ` Paul Mackerras
2008-05-03  8:03       ` Christian Stimming [this message]
2008-05-02 12:56 ` Paul Mackerras
2008-05-02 18:30   ` Christian Stimming
  -- strict thread matches above, loose matches on Subject: below --
2016-02-12 18:40 [PATCH] gitk: update " Ralf Thielow
2016-02-12 18:56 ` Stefan Beller
2016-02-12 19:17   ` Ralf Thielow
2016-03-19  6:56 ` Paul Mackerras
2010-01-27 19:30 [PATCH] gitk: Update " Christian Stimming
2009-09-25 20:41 Christian Stimming
2009-05-12 20:20 Christian Stimming
2008-01-09 21:24 Christian Stimming
2008-01-15 11:54 ` Paul Mackerras
2008-01-15 12:49   ` Christian Stimming
2008-01-08 20:56 Christian Stimming

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=200805031003.09458.stimming@tuhh.de \
    --to=stimming@tuhh.de \
    --cc=git@vger.kernel.org \
    --cc=paulus@samba.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).