unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: luangruo@yahoo.com, emacs-devel@gnu.org
Subject: Re: svg library ideas
Date: Sun, 29 Jan 2023 08:43:42 +0200	[thread overview]
Message-ID: <83h6w996xt.fsf@gnu.org> (raw)
In-Reply-To: <E1pM05H-0003PY-5h@fencepost.gnu.org> (message from Richard Stallman on Sun, 29 Jan 2023 00:18:31 -0500)

> From: Richard Stallman <rms@gnu.org>
> Cc: emacs-devel@gnu.org
> Date: Sun, 29 Jan 2023 00:18:31 -0500
> 
>   > (see INSTALL.android on the feature/android branch for the details), and
> 
> That goes beyond my knowledge of Git.  Po Lu, can you tell me how to
> access that branch?

The easiest way is to "access" it by reading the diffs of that branch
against the master branch.  Like this (after "git pull", and assuming
that your current branch is 'master'):

  $ git diff ...origin/feature/android



  parent reply	other threads:[~2023-01-29  6:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87lelo15vw.fsf.ref@yahoo.com>
2023-01-27 13:09 ` svg library ideas Po Lu
2023-01-27 16:36   ` Jean Louis
2023-01-29  5:18   ` Richard Stallman
2023-01-29  5:29     ` Po Lu
2023-01-29  6:44       ` Jim Porter
2023-01-29  6:51         ` Eli Zaretskii
2023-01-31  4:19       ` Richard Stallman
2023-01-31  5:16         ` Po Lu
2023-02-02  5:03           ` Richard Stallman
2023-02-02  5:18             ` Po Lu
2023-02-03  0:19               ` Gregory Heytings
2023-01-29  6:43     ` Eli Zaretskii [this message]
2023-02-03  6:39 Pedro Andres Aranda Gutierrez
2023-02-03  8:00 ` Eli Zaretskii
2023-02-03 11:25   ` Jean Louis
2023-02-03 12:31     ` Po Lu
2023-02-03 13:37       ` Jean Louis
2023-02-03 12:42     ` Eli Zaretskii
2023-02-03 13:56     ` Yuri Khan
2023-02-04  7:06       ` Jean Louis
2023-02-04  8:49         ` Eli Zaretskii
2023-02-04 18:38           ` Jean Louis
2023-02-05  4:29             ` Richard Stallman
2023-02-04  7:07       ` Jean Louis

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83h6w996xt.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=rms@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).