From: Claudius Heine <ch@denx.de>
To: Claudius Heine <claudius.heine.ext@siemens.com>,
Henning Schild <henning.schild@siemens.com>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH 2/2] integrate ubifs image type
Date: Tue, 29 Jan 2019 10:26:28 +0100 [thread overview]
Message-ID: <154875398897.7929.15412282169649766110@ardipi> (raw)
In-Reply-To: <20190129101050.7681afdc@md1za8fc.ad001.siemens.net>
[-- Attachment #1: Type: text/plain, Size: 1931 bytes --]
Quoting Henning Schild (2019-01-29 10:10:50)
...
> > >> Do you think that refactoring should be part of this patchset?
> > >
> > > I am not sure, just wanted to write it down. On the one hand it
> > > would be nice to solve all drive-by issues as we go. On the other
> > > hand that will slow down development and impose on contributors.
> > > So feel free to ignore my comments, the inconsistencies are not your
> > > fault and asking you to fix them would be too much.
> >
> > Maybe we should open issues for all those inconsistencies and
> > annoyances, so that they can be fixed or at least be documented.
>
> We do not use issues, so we would need another way to track not fully
> resolved discussions from the list. But i agree, it would be nice to
> keep track of things in a structured way to fix them eventually.
> Maybe a TODO.md?
I am not really a fan of TODO lists that are checked into the VCS.
I would find it very strange to send patches to the TODO list... I don't
even know what the process there would be? Should I first send a patch
to the TODO list and then have discussions about it and afterwarts start
working on patches in isar?
I rather have some uncoupled list of TODO items somewhere without the
patch/review overhead.
> > At some point making a complete code review (not just patches) on
> > isar would be great, just to find and fix those.
>
> I thought the same, maybe an Isar hackathon.
Maybe... I am not a hackathon expert. I don't know if quality codes
comes out of that...
Claudius
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de
PGP key: 6FF2 E59F 00C6 BC28 31D8 64C1 1173 CB19 9808 B153
Keyserver: hkp://pool.sks-keyservers.net
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
-----BEGIN PGP SIGNATURE-----
iQIzBAABCAAdFiEEb/LlnwDGvCgx2GTBEXPLGZgIsVMFAlxQHEEACgkQEXPLGZgI
sVMU7Q//V9y0LiS+yeGgeOXctxeJOzZMzyDc4AuNAnV2aRoFVsnb4LTylS3OLpof
zqQwGe4NszJpI/pLvyyH2vagrozC14AMWXEEAqsgUsN3XbLP92cljrvT8DI/YSzS
Vvk22CQK0eVkb3+JpftGHSwq4bIFKONzSOkKOzdh3HIXKTCbn47PeTvUX0qzGRGB
/rf5BiHIENPYntYPgNCFp9JIFcoskN63ANUgmcyDEaKaOEAugMBcwvqG9PMAoQN3
iza2M9cAOKavNMNReNtM7BCAe5umaytGY2FCLl+UMhRH96pivHNOeSQvUccBKWxV
2QDEM/d4MOdy1V2uZR+OAhvP7gFQyb1OGUwlkCg6GTWTe97AY+hpOo/BiiXLr3fu
F33EXDU+EI095F1/z6fZyqVPiwvZ9mvatRWA1PhipnoEEsuJX9DHheG8faawjk5J
e1hFoC/Jft00iNLDJ6aVfFz+hPeIR3s+A0i4X+ZkCFHLubu0IUx4p5mQbMlpdD8E
DaKPNts3i1NUXuR5cGOJOfUwnhegugRL4hvkVfQdAR3ColSLsHFNf83rVIggBa6m
wME68g+/70z60ZVJoRMsgrZkeO43yHOTJibF59eeczpMWlWGkBvcjLf+ydDiB75k
+aw/aExE/abmIPWMnIne33kMcy/9ibLkpzjllY1K+oxifvip6FA=
=52NA
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2019-01-29 9:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 12:28 [PATCH 0/2] Integrate UBIFS support (+doc fixes) claudius.heine.ext
2019-01-28 12:28 ` [PATCH 1/2] doc/user: added targz-img to image type list claudius.heine.ext
2019-01-28 12:28 ` [PATCH 2/2] integrate ubifs image type claudius.heine.ext
2019-01-28 12:36 ` Jan Kiszka
2019-01-28 12:41 ` Claudius Heine
2019-01-28 13:03 ` Henning Schild
2019-01-28 13:40 ` Claudius Heine
2019-01-28 17:22 ` Henning Schild
2019-01-29 8:16 ` Claudius Heine
2019-01-29 8:24 ` Claudius Heine
2019-01-29 9:14 ` Henning Schild
2019-01-29 9:10 ` Henning Schild
2019-01-29 9:26 ` Claudius Heine [this message]
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=154875398897.7929.15412282169649766110@ardipi \
--to=ch@denx.de \
--cc=claudius.heine.ext@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
/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